Re-opened from #3048 (auto-closed when spacedrive-data was merged into main). Rebased onto current main.

Summary

• updateSingleResource seeded the TanStack cache with { files: [...], total_count, has_more } when oldData was null (buffer replay race). This list-shaped fallback broke single-resource queries like libraries.info where the response is a plain Library object, causing TypeError: Cannot read properties of undefined (reading 'total_capacity') on the Overview page.
• Returns undefined instead (TanStack no-op) so the queryFn delivers the correct shape. Batch seeding in updateBatchResources is preserved for file listings.

Root Cause

The subscription manager pre-registers the listener before transport.subscribe() (correct for capturing buffer replay). When the daemon has a recent ResourceChanged for library (from recalculate_statistics()), the buffer replay delivers it before the queryFn resolves. With oldData null, the fallback creates { files: [Library] } which has no statistics key, crashing the Overview component.

Why only updateSingleResource

updateBatchResources keeps its { files: [...] } seeding because ResourceChangedBatch events are only emitted by the file indexing pipeline, where the list shape is correct. Single ResourceChanged events affect all resource types (library, device, volume, location, tag), most of which don't use list-shaped responses.